Progress meters in parallel computing

ABSTRACT

Systems and methods may provide a set of cores capable of parallel execution of threads. Each of the cores may run code that is provided with a progress meter that calculates the amount of work remaining to be performed on threads as they run on their respective cores. The data may be collected continuously, and may be used to alter the frequency, speed or other operating characteristic of the cores as well as groups of cores. The progress meters may be annotated into existing code.

TECHNICAL FIELD

Embodiments generally relate to progress meters. More particularly,embodiments relate to progress meters in parallel computing.

BACKGROUND

Computer architectures have grown in complexity from architectures usinga single processor to architectures using parallel processors. Inaddition, High Performance Computing (HPC) may utilize processor groupsto handle tasks according to various computational topologies andarchitectures. For example, an HPC application or job may be dividedinto various tasks that may be subdivided into groups of relatedsubtasks, commonly referred to as threads, which may be run in parallelon a computational resource. In some architectures, related threads maybe processed in parallel and completion of a task may require thecompletion of all related parallel threads that make up the task.

Computational efficiency may be enhanced by allowing parallel threads tobe completed and/or to reach a milestone (e.g., a synchronization point,a global synchronization barrier, or more simply, a barrier) beforeprogressing for further processing (if not already totally completed).Generally, individual threads may perform independent computationsbefore they reach a synchronization point. The threads may completetheir work at different times, however, due to variability ofcomputational work among various kinds of tasks, differences that mayarise in computational conditions, and so on. Thus, there may be a loadimbalance among the computational resources employed, with some threadswaiting for other threads to complete. The load imbalance may lead toinefficiencies in performance and power utilization, since computationalresources may be idle while waiting for remaining tasks to be completed.

BRIEF DESCRIPTION OF THE DRAWINGS

The various advantages of the embodiments will become apparent to oneskilled in the art by reading the following specification and appendedclaims, and by referencing the following drawings, in which:

FIG. 1 is a schematic diagram of an example of variations generated inparallel processing of a group of threads;

FIG. 2 is a schematic diagram of an example of a time-line to process athread according to an embodiment;

FIG. 3 is a flowchart of an example of a method of using progress metersaccording to an embodiment;

FIG. 4 is a flowchart of an example of a method of using progress metersin software according to an embodiment;

FIG. 5 is a block diagram of an example of a system to use progressmeters according to an embodiment;

FIG. 6 is a flowchart of an example of a method of using progress metersto vary performance of a core according to an embodiment; and

FIGS. 7A-7B are schematic diagrams of examples of variations generatedin parallel processing of a group of threads according to an embodiment;

FIG. 8 is a block diagram of an example of a system to use progressmeters at a node level according to an embodiment.

DETAILED DESCRIPTION

Computational resources may be considered, and/or grouped together, in avariety of different levels, according to a number of differenttaxonomies, and so on. For example, there may be a single processorhaving a single core at an atomic level. Above the atomic level, theremay be processors including multiple cores. A node may refer to anindividual computer including at least one processor and a networkconnection, and/or multiple processors each including multiple cores. Inone example, a node may include 16 multi-core processors. At a higherlevel, a group of nodes may be grouped together. For example, two ormore nodes may be arranged in a cabinet (e.g., a rack), wherein two ormore cabinets may be arranged in rows of cabinets. In addition, groupsbetween approximately 1,000 to 10,000 (and more) nodes may be connectedtogether to form an individual cluster, wherein clusters may beconnected to other clusters, and wherein groups of clusters may formgrids.

In HPC, nodes that comprise an individual cluster and/or a plurality ofclusters may be co-located in a common facility. Generally, a commonfacility may be served by a common power system. Clusters and/or nodesthat are co-located together in a common facility may be connected toone another by a relatively low latency, high bandwidth fabric. Inaddition, communications among remote clusters and/or nodes may beaccomplished using a network having relatively higher latency andsubstantially lower bandwidth (e.g., the Internet). Moreover, an HPCsystem may be homogenous. For example, hardware that comprises nodes maybe built to a common specification. Also, nodes of an HPC system mayshare a common file system

Each level (e.g., core, processor, node, cabinet, cluster, grid, etc.)may refer to a computational resource. In parallel processing, multiplecomputational resources may be used in a solution of a problem. Althoughportions of the following discussion may include cores for illustration,embodiments presented herein may utilize computer resources at a varietyof levels (computational resources), including processors, nodes,cabinets, clusters, grids, etc., or any combination thereof

Generally in HPC, an application may refer to a “job” and a job mayinclude a number of tasks that may be broken down into individualsubtasks, which may be referred to as “threads.” In parallel computing,a task may be broken down into a related group of independent threadsthat may be ran concurrently in parallel with one another, wherein eachthread may run on a separate core within a node. The threads thatcollectively make up a given task may run on the cores or processorswithin a given node. The threads of a given task may run on multipleprocessors within a node when, for example, the processors share thesame coherent memory space. In addition, the threads of more than onetask may be ran on a given node based on, for example, a number ofmicroprocessors and/or cores in the node, a workflow being presented,and so on. Additional architectures may permit variations. For example,in some variants, multiple threads may share a common core throughvarious forms of multiplexing.

In parallel processing, code that is to be processed in a parallelfashion may break into individual instances (copies) of itself.Instances may refer to a “rank” in one form of parallel processing thatuses a programming model based on a communication library and a runtimecalled Message Passing Interface (MPI).

A thread may represent a series of work assigned to the thread, orsimply “work.” Generally, a first set of work undertaken in a thread mayneed to be completed before remaining work in a thread may begin. Thework undertaken by a parallel group of threads within a task may becompleted when all of the threads in the parallel group of threads havereached a common milestone in terms of the work that the group hascompleted. Commonly, it may not be desirable for a new task to commencebefore the processing of a previous task, of relevance to the new task,has completed. One approach to preventing such a situation from arisingis to provide a barrier for the individual parallel threads to reach,wherein the parallel threads have each completed a certain definedamount of work allotted to them at the point represented by the barrier.In this regard, the threads may be in a state of synchronicity with oneanother. Barriers may be scheduled in time (e.g., occurring with aparticular frequency) and/or may be event-based, occurring when thethreads complete some amount of work that is computed and assigned atinitialization and/or when a previous barrier was reached. The provisionof barriers may refer to barrier synchronization, and the barrier mayrefer to a synchronization barrier, or simply, a “barrier.”

Parallel processing may utilize synchronization barriers as globalbarriers, at which all related threads pause until each of the threads(e.g., processing each on its respective core) have completed the workthat has been assigned to each of the threads. Again, and depending onthe architecture, global barriers may be time-based and/or may beevent-based.

Ideally, all threads would arrive at a given barrier (e.g., a globalbarrier) at the same time. Generally, threads that make up a task maytake different times to complete, even when the computational resourcesemployed appear to be identical (e.g., when cores have been designed toa common specification), and even when the problem has been broken downin what appears to be equal sized portions (e.g., in a large sort,wherein each node may be given a fixed, equal fraction of the data tosort). There may be a number of causes for such variations. Commonly,the causes may be characterized as being “static” or they may becharacterized as being “dynamic.” In the static case, the cause may bemore or less invariant over time, whereas some variability in anoperating characteristic arises over time in the dynamic case.

One source of static variability may include as-manufactured variabilityof hardware. Even though every processor may nominally be identical toevery other processor, manufacturing processes may admit some variationin processor qualities, such as processor frequency, speed, and so on.

Examples of dynamic sources of variability include Input/Output (I/O)interrupts from the Operating System (OS), which may slow down aprocessor. Wake up times, for example due to I/O calls, may vary overtime as well, as may a frequency and/or a moment at which a node may beinterrupted by an OS. Memory accesses that are made by tasks executingon processors may require varying amounts of time to service, dependingon the task. Additional sources of variability may include jittereffects, for example, from the OS interrupting threads on one coreand/or processor differently than other threads to perform OS dutiessuch as, e.g., updating a clock, running system software to support anapplication, and so on. Another dynamic source of variability may befrom recoverable hardware errors occurring differently from one node toanother node.

Still other sources of variability may be from the nature of a job beingprocessed. For example, task may not divide evenly among resources,either at the software level, or in terms of allocation of hardware(e.g. processors, nodes, etc.) to the job and/or tasks.

Whatever the sources of variability, addressing variability consequencesmay require that cores tasked with processing a related set of threadswait at periodically placed global synchronization barriers (or simply“barriers”).

Turning now to FIG. 1, an example of waiting times that may occurbetween a first global synchronization barrier 12 and a subsequentglobal synchronization barrier 14 is shown. A series of threads T1, T2,T3 . . . , Tn (T1 to Tn), which may correspond to a set of relatedsubtasks of a task, begin to be processed at an initial time t_(o)marked on a time scale 10. The length of bars representing each of thethreads T1 to Tn corresponds to a duration during which the threads mayundergo processing by their respective cores and/or processors within agiven node. For example, the thread T1 may include an active period ofprocessing and/or running time 16, followed by a waiting time 18 duringwhich its core waits for the other threads T2, T3, . . . Tn that areprocessing in other cores to complete their assigned work and therebycatch up to the thread T1.

Each of the threads T1 to Tn may be referred to as active whenundergoing processing on its respective core for a respective period ofrunning time 16 as the work allotted to the threads T1 to Tn isaccomplished. It should be understood that active periods, i.e.,respective periods of running times 16 associated with each of the nthreads, may vary with respect to one another. In FIG. 1, the thread T1takes the least amount of time to complete (e.g., finish) and the threadT3 taking the longest amount of time to complete (e.g., finish).

A global synchronization barrier 14 may be provided, wherein furtherprocessing of threads on cores may be held back (e.g., paused) until theslowest of the threads has completed processing on its respective core.As discussed above, the synchronization barrier may be event-based,and/or it may be time-based. In addition, a spacing of barriers may befixed and/or may vary. Moreover, barriers may arise throughout the lifeof a thread. In addition, variation in running times 16 may result invariations in waiting times 18 for each of the cores, during which somethreads may be idle and/or their respective cores may not be processingthreads. Thus, waiting times may entail idling, which may be wasteful ofhardware resources.

It may be possible to reduce the total waiting times by reallocatingcomputational resources (e.g. a number of cores, processors, nodes,etc., at work on a task). In some embodiments, waiting times at a corelevel may be reduced overall by speeding up slower cores while slowingdown faster cores to allow threads and/or cores to arrive at a globalsynchronization barrier in relatively less mean time. In one embodiment,speed control over a core may include changing an operating frequency ofcores, wherein the operating frequency may determine the speed of thecore in processing threads under some circumstances and under somemetrics. Core frequency may scale with an amount of power provided tothe core. In addition, power may scale with a square of the voltagesupplied to the core.

In one embodiment, scaling may be leveraged by obtaining informationconcerning a speed with which threads complete their work before thethreads' next global synchronization barrier, and using that informationto affect the speed of the cores by adjusting an amount of powerprovided to the cores. Although the use of scaling is discussed withrespect to a core as a computational resource, a similar approach may beundertaken with respect to aggregates of cores, processors, nodes,cabinets, clusters, grids, etc., to allow aggregates of cores to runrelatively more efficiently in terms of power and/or time.

Information concerning a speed with which threads may complete theirwork may be provided by a series of progress meters. In someembodiments, progress meters may be provided as part of the code that isrun on the cores. The progress meters may compute an amount of work thata thread is to complete before a next synchronization global barrier.Then, at intervals thereafter (either periodic or not), the progressmeters may compute an amount of work remaining until the next globalsynchronization barrier is reached. Information on the progress ofthreads may be subsequently used to control a frequency (e.g., speed) ofcores and/or an allocation of computer resources.

FIG. 2 shows an example of an embodiment in which a progress meter maybe used to track progress of a single thread executing on a single core.At a time Ts1, a first global synchronization barrier 21 marks a startof processing and a thread globally synchronizes with other relatedthreads across respective cores of the threads. In one example, theprocessing begins with a serial code region 22 in which threads may beprocessed serially. At time 24, the thread arrives at a parallel coderegion 28, at which point a progress meter (which may be imbedded intothe parallel code) computes the total work to be done in processing thethread from start to completion prior to reaching a next globalsynchronization barrier. Although FIG. 2 depicts a serial code region 22preceding a parallel code region 28, in other embodiments the serialcode region 22 may follow or be interleaved with the parallel coderegion 28. Indeed, there may be multiple serial and parallel coderegions between barriers.

At subsequent times 30, the progress meter computes a percent of totalwork remaining and/or completed at the particular point in time (i.e., a“work fraction”) and shares the work fraction with other system assets,discussed below. At time Ts2, a second synchronization barrier 31 may beprovided, followed by a serial code region 32. A new calculation of anamount of work to be done may occur at time 34 for further processing ofthe thread (e.g., if the thread has not already completely completed orbeen discarded) as the thread enters the next parallel code region 38.At subsequent times 40, a percent of total work remaining and/orcompleted at the particular point in time (i.e., the work fraction) mayagain be calculated, and the work fraction may be shared with othersystem assets, discussed below. In addition, the thread continues andreaches a next synchronization barrier 41 at time Ts3. The processrepeats for each thread in a group of threads until the overall jobrepresented by the group of threads has been completed.

Turning now to FIG. 3, a flowchart of an example of a method 50 in whichprogress meters in software may be used to track a completion of athread in a node is shown according to an embodiment. The method 50 maybe implemented as a set of logic instructions stored in a machine- orcomputer-readable storage medium such as random access memory (RAM),read only memory (ROM), programmable ROM (PROM), flash memory, etc., inconfigurable logic such as programmable logic arrays (PLAs), fieldprogrammable gate arrays (FPGAs), complex programmable logic devices(CPLDs), in fixed-functionality logic hardware using circuit technologysuch as application specific integrated circuit (ASIC), CMOS ortransistor-transistor logic (TTL) technology, or any combinationthereof. For example, computer program code to carry out operationsshown in the method 50 may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. Moreover, the method 50 may be implemented using any of theherein mentioned circuit technologies.

A job may start at block 52. At illustrated processing block 54, a coreand the core's attendant thread may be globally synchronized withrespect to other related threads and cores, giving the threads a commonstarting time. After executing any serial code that may be present, thethread encounters a parallel code region at illustrated processing block56. At illustrated processing block 58, a progress meter calculates anamount of work that is to be processed before the thread encounters abarrier. At illustrated processing block 60, the code may be executed,for some period at the end of which illustrated processing block 62computes how much work, either in absolute terms or as a fractionalrepresentation thereof (e.g., as a percentage), remains to be done onthe thread. Information regarding remaining work is shared with amonitor Application Processing Interface (API) at illustrated processingblock 64. Block 65 determines if the thread has completed (i.e., if allof the work to be done in the thread has been done). If the work has notbeen completed, then control passes back to the processing block 60,wherein additional processing occurs. If the block 65 determines thatthe work has completed, then illustrated processing block 66 determinesif the overall job has been completed. If so, then the process ends atblock 68. On the other hand, if there are additional threads for thecore to process, then control passes back to the processing block 54 foranother synchronization.

Progress meters offer a possibility of providing multiple evaluations ofwork remaining in a thread, and thus offer information that may beutilized to alter work flow in approaches that are relatively moreefficient users of resources, including time and computationalresources. Jobs may then be completed relatively sooner than inconventional approaches.

Progress meters may be implemented in software. In one embodiment, theimplementation may be as a software probe that may be inserted intoexisting code. Such a probe may be referred to as a call statement whichwhen encountered calculates work to be done in processing a thread onits initial encounter, and then calculates a fraction of that workremaining to be done for the thread in subsequent encounters.

FIG. 4 shows an example 70 of an embodiment of a software implementationof a progress meter, which illustrates an annotation of pre-existingcode with a progress meter. In the example 70, the pre-existing codethat begins at block 72 is a simple loop. At illustrated processingblock 74, the software may be passed a parameter indicating that it isto be executed J times. A variable K may be employed as a counter fortracking the number of passes through the code, and initialized to aninteger 1 at illustrated processing block 76. The code may be executedat illustrated processing block 78, and the variable K may beincremented at illustrated processing block 80. Block 82 determines ifK=J. If K does not equal J, then control loops back to the processingblock 78. If the block 82 determines that K=J, then the code may finishrunning at illustrated processing block 84.

A progress meter 86 may be provided in the form of an API that may beinserted into or in parallel with existing code as in FIG. 4. Theprogress meter 86 may be passed the value of J and it may track thenumber of loops that have been made and/or are yet to be made throughthe code. Access to the code that is to be executed, along with both thenumber of iterations through the code that have been made (e.g., K) andthe number of iterations that are to be made (e.g., J) may provide ameasure of progress made at a level of each iteration through the loop.For example, if J=10, then when K=1 it may be determined that 10% ofwork on a thread has been completed. In another example when K =8, itmay be determined that 80% of work has been completed. Alternatively,these numbers may be expressed as percentage of work that remains to becompleted (e.g., in the first example, 90% of the work remains to bedone, and in the second example, 20% of the work remains to be done).The progress meter 86 may pass numbers indicating the amount of workcompleted and/or to be completed to a runtime monitor API, discussedbelow, to affect the processing of the threads.

In other embodiments, a progress meter may determine total work and/orpercent work completed automatically through dynamic code profilingand/or analysis of processor performance counters. In addition, anapplication may not pass other information to a progress meter.

A progress meter may compute work and/or work percentages either on atime-based scale (i.e., having a certain number of occurrences/unittime, or frequency), or the progress meter may be event based (e.g.,making a computation each time through a loop regardless of time, suchas is the case in the example in FIG. 4, discussed above. In oneembodiment, a progress meter may update approximately once every 10micro-seconds. Faster updating may be employed. If updates are computedrelatively frequently, and the progress meter is inserted into theapplication code serially (and not in parallel with it), overhead and/orapplication performance may be balanced and/or considered.

Turning now to FIG. 5, a block diagram of an example of a system toutilize progress meters is shown according to an embodiment. In oneexample, computational resources may include cores. For example, a groupof cores may be provided including a first core 87 and an Nth core 88.Each of the cores 87 . . . 88 may run a thread 90-1 . . . 90-N that maybe an instance of parallel code, which may be identical from core tocore. Each core 87 . . . 88 may be provided with a progress meter 92. Inone example, the progress meters 92 of each of the cores 87 . . . 88 maynotify a runtime monitor 94 (which may itself be an API) of the progressbeing made on a thread via explicit function calls. Alternatively, theprogress meters 92 of each of the cores 87 . . . 88 may update progressvalues that may be queried by the runtime monitor 94. The runtimemonitor 94 may be a part of the OS, a stand-alone program, or a part ofa relatively comprehensive performance/power optimization framework thatcombines multiple optimization techniques.

At a first global synchronization point, the progress meters 92 of eachof the cores 87 . . . 88 report the total amount and/or percentage ofwork that is to be completed with respect to a given thread from startto completion. Then, at subsequent intervals, the progress meters 92 ofeach of the cores 87 . . . 88 report a fraction of work remaining(and/or already completed—the work fraction). The runtime monitor 94forwards the work fraction to a performance balancer 96, which may usethe information provided by the progress meters 92 to modify a frequencyof each of the cores 87 . . . 88, and/or otherwise affect an allocationof resources applied at the core level.

The information provided by the progress meters 92 of each of the cores87 . . . 88 may be used in a number of ways. In the event that a threadtraverses a given core at a slower speed than other threads aretraversing respective cores, the slower core may be sped up and/or thefaster core slowed down by varying respective frequencies of the cores.One way to affect such control is by reallocating power from the fastercores to the slower cores. Similarly, adjustments to the power suppliedto cores or other adjustments to the cores that affect their operatingfrequency, may, in the aggregate, also modify the speed of theirrespective nodes and aggregates of nodes.

Thus, core (and/or processor) frequency may be varied over a range byaltering the amount of power that may be fed to the core (and/orprocessor). In a situation where power resources may be limited, fasterthread processing times may be obtained by shifting power away fromcores that are faster than the average of the cores employed, and towardcores that are slower than the average of the cores employed. In somecircumstances, it may be advantageous to redirect power away from coresthat are slower than average to other cores that are even slower.Progress meters provide data that may be used to regularly adjust powerto cores, thereby relatively reducing waiting times at synchronizationpoints. In some embodiments, power shifting may also reduce powerconsumed in the course of processing a given job.

FIG. 6 shows a flowchart of an example of a method 100 of utilizinginformation provided by progress meters to control the flow of poweramong the cores in a node. The method 100 may be implemented as a set oflogic instructions stored in a machine- or computer-readable storagemedium such as random access memory (RAM), read only memory (ROM),programmable ROM (PROM), flash memory, etc., in configurable logic suchas programmable logic arrays (PLAs), field programmable gate arrays(FPGAs), complex programmable logic devices (CPLDs), infixed-functionality logic hardware using circuit technology such asapplication specific integrated circuit (ASIC), CMOS ortransistor-transistor logic (TTL) technology, or any combinationthereof. For example, computer program code to carry out operationsshown in the method 100 may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. Moreover, the method 100 may be implemented using any of theherein mentioned circuit technologies.

Illustrated processing block 102 may collect data from progress metersregarding an amount of work remaining to be performed on related threadsat respective cores of the related threads. The data may be stored invector or matrix form. It may be desired to increase an amount of datacollected. Thus, block 104 determines if enough data has been collected.If not, control passes back to the processing block 102. If so, thenillustrated processing block 106 calculates numbers provided by theprogress meters across the cores. One useful measure may include a skewof the samples collected, where the skew may refer to a variance of thecore progress (as determined in the samples) divided by their mean.

When the skew lies within some limit, the operation of the cores may bedetermined to be efficient in terms of time and/or power resourcesemployed. Thus, block 108 determines if the skew may be within a bound.If so, control loops back to the processing block 102 for another roundof data collection. If the skew is outside of a bound set by the limit,then a median of the samples for the cores may be computed atillustrated processing block 110, and the cores may be sorted about themedian (e.g., from high to low) at illustrated processing block 112.

Illustrated processing block 114 arranges the cores in pairs, beginningwith the fastest core being paired to the slowest core, continuing withthe second fastest core being paired to the second slowest core, and soon in round-robin fashion until all cores and/or all cores lying outsideof some predetermined band are accounted for. Illustrated processingblock 116 steers power within each pair of cores from the faster of thetwo cores to the slower of the two cores. Such power shifting may slowdown the faster cores (e.g., in the pairs) by reducing the operatingfrequency of the faster cores (e.g., in the pairs), and/or may speed upthe slower cores (e.g., in the pairs) by increasing the operatingfrequency of the slower cores (e.g., in the pairs) .

Advantageously, the overall speed with which a parallel processing jobis to be completed may be relatively increased. In addition, totalamount of power necessary to complete the job may be relatively reduced.Moreover, facilities that house HPC systems generally may requiresubstantial air cooling to account for heat generated at the cores of anHPC system. Thus, reducing the relative power consumed by the cores mayresult in less heat generated at the cores, which may allow relativelyless intensive use of air conditioning systems in HPC facilities toprovide additional further power savings.

In an alternative embodiment, the processing block 114 may omitted, andthe slowest frequency cores may be boosted at illustrated processingblock 116 by, for example, directing that they receive more power, whichmay be accompanied by reductions in the amount of power provided to thefaster cores.

The processing blocks may be implemented in the various combinations ofhardware and/or software elements noted above. Thus, in one embodimentprocessing block 106 may be implemented in hardware and/or software, andmay include a skew calculator to compute a skew. It will be appreciatedthat other implementations of the method are possible.

Turning now to FIGS. 7A-7B, several effects of data provided by progressmeters to control computational resources, such as cores, is shownaccording to an embodiment. In one example, core frequencies may bevaried (such as by varying the power supplied to the cores). FIG. 7A issimilar to FIG. 1, discussed above, and shows a time interval along atimeline 120 between an initialization 122 of a group of threads T1, T2,T3, . . . Tn at a time to and a time t_(b), at which a subsequentsynchronization barrier 124 may be encountered.

Each of the threads T1, T2, T3, . . . Tn may have a respective activerunning time 126 during which work occurs, and may have a respectivewaiting time 128 during which work on a thread has completed, and duringwhich the thread and/or the core on which the threads run awaits otherthreads to complete work on the other threads' respective cores. In theillustrated example, the waiting times of the threads T1, T2, T3, . . .Tn are indicated as WT1, WT2, WT3 . . . WTn, respectively. Some of thewaiting times may be 0, and in general some of the waiting times may belonger than others. The sum of the waiting times may be given as:

W _(total) =WT1+WT2+WT3+. . . WTn

FIG. 7B shows a situation in which one of the embodiments discussedherein is employed to vary a frequency of individual cores, speeding upthose that are relatively slow and/or slowing down those that arerelatively fast. A time interval is shown along a timeline 130 betweenan initialization 132 of a group of threads T′1, T′2, T′3 . . . T′n attime t′₀ and a time t′_(b), at which a subsequent synchronizationbarrier 134 may be encountered. Each of the threads T′1, T′2, T′3 . . .T′n may have an active running time 136 during which work occurs, andmay have a waiting time 138 during which work on a thread has completed,and during which the thread and/or the core on which the threads runawaits other threads to complete work on the other threads' respectivecores. In the illustrated example, the waiting times of the threads T′1,T′2, T′3 . . . T′n are indicated as WT′1, WT′2, WT′3 . . . WT′n,respectively. Some of the waiting times may be 0, and in general some ofthe waiting times may be longer than others. The sum of the waitingtimes may be given as:

W′ _(total) =WT′1+WT′2+WT′3+. . . WT′n

It may be noted that the effect of utilization of progress meters may beto permit a synchronization barrier 134 to be encountered sooner thanwould be the case as depicted in FIG. 7A. For example:

(t _(b) −t ₀)>(t′ _(b) −t′ ₀)

Moreover, the total of the waiting times may be relatively reduced whenusing data provided by the progress meters:

W _(total) >W′ _(total)

Reductions in waiting times may permit a shortening of intervals betweenglobal barriers and may make relatively more efficient use ofcomputational resources in terms of time and/or power used in completingjobs.

Although examples of embodiments set forth here have been presented interms of cores as the basic unit of computational resource, embodimentsmay also be applied to other levels of computational resource, includingprocessors, multi-core processors, racks of nodes, cabinets, clusters,grids, and so on. Embodiments at levels above the core, such as nodes,may include aggregating data from the cores of related threads runningon a given node.

FIG. 8 shows a block diagram of an example of a system to use progressmeters at a node level (e.g., computational resources are nodes). Agroup of nodes may be provided including a first node at 186 and an Nthnode 188. Each of the nodes 186 . . . 188 may run one or more tasks 190that may be instances of parallel code, which may be identical for arelated group of tasks running within a given node. As before, each taskmay include a number of related threads, each of which may run on asingle core. Each node may include a number of cores on which a numberof threads are being processed, each of which may be provided with aprogress meter 192 that may report to a runtime monitor 194 (which maybe an API) at various times. Thus, embodiments may include aggregationsof cores, e.g., nodes.

At the level of nodes, the progress meters 192 of each of the nodes 186. . . 188 may provide statistical measures based on aggregates for thevarious threads and/or tasks that are executing in the respective nodes186 . . . 188. For example, the progress meters 192 of each of the nodes186 . . . 188 may report an average work completed and/or to becompleted across cores in a given node. In another example, the progressmeters 192 of each of the nodes 186 . . . 188 may report a number toindicate the least amount of work completed in any one of the cores in anode.

Other statistical measures (e.g., median, variance, standard deviation,skew etc.) of core performance within a given node may be also reported.At subsequent intervals based on time and/or event, the progress meters192 of each of the nodes 186 . . . 188 may continue to report statisticsderived from work completed and/or work assigned to the computationalresources (e.g., cores) within each of the respective nodes 186 . . .188. The runtime monitor 194 forwards the information to a performancebalancer 196, which may use the information provided by the progressmeters 192 of each of the nodes 186 . . . 188 to modify the allocationof resources applied to the nodes. Additionally, the performancebalancer may aggregate the per-thread progress meter informationprovided regarding individual threads to determine overall nodeprogress.

Adjustment of node power, which may be used to alter node speed, may beaccomplished through a variety of mechanisms. For example, a processormay be equipped with software-exposed power capping and monitoringinterfaces that a runtime system configures to adjust processor power.

At still higher levels, where it is desired to track progress ofindividual cabinets, clusters, and/or grids, basic informationconcerning work progress may continue to be based on per-thread dataprovided at the core level by the progress meters, discussed above. Asone moves to higher levels of computational resource, progress meterdata may be progressively aggregated, level by level. For example, whenevaluating the speed of nodes, one may consider the slowest thread onany core within a given node, and may use that as a proxy for the speedof the node. Similarly, when considering the progress of aggregations ofnodes (e.g., in clusters), one may further aggregate node data byconsidering the slowest node in a cluster as a proxy for the speed ofthat cluster. The speed of the slower computational resources (node,cluster, etc.) may then be modified by speeding up the slower performingcomputational resources, possibly while also slowing down the fasterperforming computational resources. One way of affecting speed may be byproviding more power to slower resources.

In an additional embodiment, the process times for relatively slowprocessing threads may be decreased by providing the relatively slowerthreads with additional resources, such as by further dividing the workof a thread and then parceling out the divided thread to additionalcores.

Embodiments disclosed herein may mitigate the problem of load imbalanceand provide methods to speed up tasks that otherwise might take longerto complete while allowing tasks that otherwise might complete faster torun in a more power efficient regime. Notably, tasks that are runningslow may be sped up by being given additional resources. The resourcesmay include additional electrical power provided to processing cores.Such an approach may use metrics of task completion. In embodiments, themetrics may be provided by providing progress meters as annotations toparallel computational regions that indicate a fraction of work betweensynchronization points a particular thread has performed.

In addition, load balancing may be provided in cases when computationalwork may not commonly be evenly balanced between parallel tasks andsubtasks (threads). Such cases may arise when available computationalresources may not divide evenly, or the problem might have some affinityto powers of two or to perfect cubes, but a number of cores may bearbitrary, etc. For irregular problems (graphs, adaptive grids), optimalwork balancing may be difficult, and the physical resources at hand maynot be evenly divisible by the tasks at hand. Embodiments may providedynamic balancing among the tasks and threads.

The progress of each task may be expressed in units that are specific toparticular applications. For example, in loop-based regions ofcomputations, e.g., as is depicted in FIG. 4, discussed above, which maygenerally be in HPC applications, progress may be expressed as afraction of loop iterations performed between synchronizations. Apractical advantage of using workload-specific metrics for trackingapplication progress may include objectively representing completed workindependent of code generation or run time conditions.

Using a system-observable metric, such as a count of instructions and/orspecific operations, as a proxy for application progress may need toaccount for a compiler that generates two or more versions of the samecode region (vector and scalar, parallel and serial) with one of theversions being picked dynamically at run time based on some condition.Different run time choices may distort application progress monitoringwhen based on instruction or operation counts. Using workload-specificmeasures of progress may provide more global consistency across multiplenodes.

In some embodiments, a run-time monitor program may be used to trackprogress of parallel tasks and identify which tasks are falling behindthe slowest value across all tasks in a group. The run-time monitor maythen apply additional resource to the lagging tasks to equalize taskprogress. The additional resources may include an increased power budgetfor a particular task that may allow corresponding CPU cores to run athigher frequencies, therefore speeding up the progress. In a case ofapplications parallelized at multiple levels, such as hybrid MessagePassing interface (MPI)/Open Multi-Processing (OpenMP) applications, themonitor program may dynamically increase a number of OpenMP threads thatare used in a slow running MPI rank. Similarly, the tasks whose progressexceeds that of the rest of tasks in parallel workload may be sloweddown by reducing their power allocation and/or an amount of otherresources, such as CPU cores, that they use, relatively improving theefficiency of the run without impacting the run time or performance.

In situations where processor speeds are effectively uniform within agiven processor type, individual processors may be allocated differentamounts of power as a default, with the amount of power allocated beingless than what may be used to power the processors at its full speed.For example, two processors that may be nearly identical may tasked withwork that may entail the use of different amounts of power. Twoprocessors may require different voltages to achieve correct operationat a given speed, and the power may be enough for one processor toachieve the voltage and not the other processor. Embodiments may be usedwith such processors to further vary performance in ways that relativelyimproves the speed of such processors and/or efficiency in parallelprocessing applications.

Embodiments presented herein may be used both in customer code and invendor-supplied libraries that may be used across multiple applications.In cases when it may be desired to annotate an entire body of code withprogress meters, a partial application of this technique to mostfrequently used regions of the code may still produce beneficialresults.

To the extent various operations or functions are described herein, theymay be described or defined as hardware circuitry, software code,instructions, configuration, and/or data. The content can be embodied inhardware logic, or as directly executable software (“object” or“executable” form), source code, high level shader code designed forexecution on a graphics engine, or low level assembly language code inan instruction set for a specific processor or graphics core. Thesoftware content of the embodiments described herein can be provided viaan article of manufacture with the content stored thereon, or via amethod of operating a communication interface to send data via thecommunication interface.

A non-transitory machine readable storage medium can cause a machine toperform the functions or operations described, and includes anymechanism that stores information in a form accessible by a machine(e.g., computing device, electronic system, etc.), such asrecordable/non-recordable media (e.g., read only memory (ROM), randomaccess memory (RAM), magnetic disk storage media, optical storage media,flash memory devices, etc.). A communication interface includes anymechanism that interfaces to any of a hardwired, wireless, optical,etc., medium to communicate to another device, such as a memory businterface, a processor bus interface, an Internet connection, a diskcontroller, etc. The communication interface may be configured byproviding configuration parameters or sending signals to prepare thecommunication interface to provide a data signal describing the softwarecontent. The communication interface can be accessed via one or morecommands or signals sent to the communication interface.

Various components described can be a means for performing theoperations or functions described. Each component described hereinincludes software, hardware, or a combination of these. The componentscan be implemented as software modules, hardware modules,special-purpose hardware (e.g., application specific hardware,application specific integrated circuits (ASICs), digital signalprocessors (DSPs), etc.), embedded controllers, hardwired circuitry,etc. Besides what may be described herein, various modifications can bemade to the disclosed embodiments and implementations of the inventionwithout departing from their scope. Therefore, the illustrations andexamples herein should be construed in an illustrative, and not arestrictive sense. The scope of the invention should be measured solelyby reference to the claims that follow.

Additional Notes and Examples

Example 1 may include a method of controlling a computational resource,comprising globally synchronizing a plurality of tasks across aplurality of computational resources, computing an amount of work tocomplete at least one task of the plurality of tasks, processing theplurality of tasks in parallel to accomplish work corresponding to eachtask of the plurality of tasks, repeatedly computing a work fractionthat corresponds to one or more of a fraction of work completed or workremaining to be completed with respect to the amount of work to completethe at least one task of the plurality of task, and modifying acharacteristic of at least one computational resource of the pluralityof computational resources based on the work fraction.

Example 2 may include the method of Example 1, wherein the plurality ofcomputational resources includes a plurality of cores, and wherein afrequency of at least one core of the plurality of cores is varied basedon the work fraction.

Example 3 may include the method of any one of Examples 1 to 2, whereinthe plurality of computational resources includes a plurality ofprocessors, and wherein a frequency of at least one core of theplurality of processors is varied based on the work fraction.

Example 4 may include the method of any one of Examples 1 to 3, whereinthe plurality of computational resources includes a plurality of nodes,and wherein at least two nodes of the plurality nodes are to processparallel code.

Example 5 may include the method of any one of Examples 1 to 4, whereinthe plurality of tasks includes a plurality of threads, and wherein theplurality of computational resources includes a plurality of cores.

Example 6 may include the method of any one of Examples 1 to 5, furtherincluding receiving an indication of the work fraction at a runtimemonitor.

Example 7 may include the method of any one of Examples 1 to 6, furtherincluding modifying one or more of a number, a distribution, a speed, ora frequency of at least one of the plurality of computational resources.

Example 8 may include the method of any one of Examples 1 to 7, whereinthe characteristic includes a speed, and wherein the speed of at leastone computational resource of the plurality of computational resourcesis modified by changing an amount of electrical power provided to the atleast one computational resource.

Example 9 may include the method of any one of Examples 1 to 8, whereinthe plurality of computational resources includes one or more of a core,a processor, a multi-core processor, a node, a cabinet, a cluster, arow, or a grid.

Example 10 may include the method of any one of Examples 1 to 9, whereinthe plurality of computational resources includes a first computationalresource, at least one set of second computational resources, whereineach of said second computational resources has a performance measure,wherein a minimum of performance measures of the second computationalresources is used as a performance measure of the set of secondcomputational resources, and wherein the set of second computationalresources is a subset of the first computational resource, and whereinthe performance of the first computational resource is the performancemeasure of the set of second computational resources.

Example 11 may include the method of any one of Examples 1 to 10,further including reporting the work fraction by one or more of anapplication or an Application Programming Interface (API).

Example 12 may include the method of any one of Examples 1 to 11,wherein at least a portion of the plurality of computational resourcesare in communication with one another.

Example 13 may include the method of any one of Examples 1 to 12,wherein the plurality of computational resources includes a plurality ofgroups of cores, and wherein the method further includes measuring anoperating characteristic of at least one group of the plurality ofgroups of cores, and modifying a speed of at least one of the groups ofcores based on the measurement.

Example 14 may include the method of any one of Examples 1 to 13,wherein the operating characteristic is speed, and wherein the methodfurther includes increasing a speed of a first group of cores byincreasing an amount of power supplied to the first group of cores, anddecreasing a speed of a second group of cores by decreasing the amountof power supplied to the second group of cores.

Example 15 may include the method of any one of Examples 1 to 14,further including synchronizing the plurality of tasks at a barrier.

Example 16 may include the method of any one of Examples 1 to 15,wherein each task of the plurality of tasks includes a waiting time atthe barrier, and wherein the method further includes repeatedlymodifying the characteristic to reduce the waiting time for at least onetask.

Example 17 may include the method of any one of Examples 1 to 16,wherein the groups of cores are nodes, and wherein the method furtherincludes calculating a skew of a plurality of measurements of anoperating characteristic for a plurality of nodes, and modifying a speedof at least one node based on the skew.

Example 18 may include an apparatus to process tasks, comprising aplurality of computational resources to process a plurality of tasks inparallel, wherein the plurality of tasks are to be globally synchronizedacross the plurality of computational resources, progress meter logic,implemented at least partly in fixed functionality hardware, to computean amount of work to complete at least one task of the plurality oftasks, and repeatedly compute a work fraction that is to correspond toone or more of a fraction of work completed or work remaining to becompleted with respect to the amount of work to complete the at leastone task, and performance balancer logic, implemented at least partly infixed functionality hardware, to modify a characteristic of at least onecomputational resource of the plurality of computational resources basedon the work fraction.

Example 19 may include the apparatus of Example 18, wherein theplurality of computational resources is to include a plurality of cores,and wherein the performance balancer logic is to vary a frequency of atleast one core of the plurality of cores based on the work function.

Example 20 may include the apparatus of any one of Examples 18 to 19,further including runtime monitor logic, implemented at least partly infixed functionality hardware, to receive information from the progressmeter logic indicative of the work fraction.

Example 21 may include the apparatus of any one of Examples 18 to 20,wherein the performance balancer logic is to vary a speed of at leastone of the plurality of computational resources by varying an amount ofpower supplied to the at least one of the plurality of computationalresources.

Example 22 may include the apparatus of any one of Examples 18 to 21,wherein the performance balancer logic is to vary a speed of at leasttwo of the plurality of computational resources by steering power from arelatively faster one of the plurality of computational resources towarda relatively slower one of the plurality of computational resources.

Example 23 may include the apparatus of any one of Examples 18 to 22,wherein the computational resources are to include a plurality of cores,and wherein performance balancer logic is to vary a frequency of atleast one of the plurality of cores by varying an amount of powerprovided to at least one of the cores.

Example 24 may include the apparatus of any one of Examples 18 to 23,wherein the plurality of computational resources are to include one ormore of a core, a processor, a multi-core processor, a node, a cabinet,a cluster, a row, or a grid, and wherein at least a portion of theplurality of computational resources are to have a communicationschannel therebetween.

Example 25 may include the apparatus of any one of Examples 18 to 24,further including a plurality of nodes, and skew calculator logic tocompute a skew of a plurality of measurements taken from the pluralityof nodes, wherein the performance balancer logic is to vary a speed ofat least one of the nodes based on the skew.

Example 26 may include the apparatus of any one of Examples 18 to 25,wherein the performance balancer logic is to modify one or more of anumber, a distribution, a speed, or a frequency of at least one of theplurality of computational resources.

Example 27 may include at least one computer readable storage mediumcomprising one or more instructions that when executed on a computingdevice cause the computing device to globally synchronize a plurality oftasks across a plurality of computational resources, compute an amountof work to complete at least one task of the plurality of tasks,repeatedly compute a work fraction that corresponds to one or more of afraction of work completed or work remaining to be completed withrespect to the amount of work to complete the at least one task of theplurality of tasks, and modify a characteristic of at least onecomputational resource of the plurality of computational resources basedon the work fraction.

Example 28 may include the at least one computer readable storage mediumof Example 27, wherein the plurality of computational resources is toinclude a plurality of cores, and wherein the instructions, whenexecuted on a computing device, cause a performance balancer to vary afrequency of at least one of the plurality of cores.

Example 29 may include the at least one computer readable storage mediumof any one of Examples 27 to 28, wherein the instructions, when executedon a computing device, cause the computing device to compute the workfraction, and receive information from the progress meter indicative ofthe work fraction.

Example 30 may include the at least one computer readable storage mediumof any one of Examples 27 to 29, wherein the instructions, whenexecuted, cause the computing device to vary a characteristic ofoperation of at least one computational resource of the plurality ofcomputational resources.

Example 31 may include the at least one computer readable storage mediumof any one of Examples 27 to 30, wherein the instructions, whenexecuted, cause the computing device to vary an amount of power providedto at least one of the plurality of cores.

Example 32 may include the at least one computer readable storage mediumof any one of Examples 27 to 31, wherein the instructions, whenexecuted, cause the computing device to allow the plurality of tasks tosynchronize at a barrier.

Example 33 may include the at least one computer readable storage mediumof any one of Examples 27 to 32, wherein each task of the plurality oftasks includes a waiting time at the barrier, and wherein theinstructions, when executed, cause the computing device to repeatedlymodify the characteristic to reduce a waiting time for at least onetask.

Example 34 may include an apparatus for controlling computationalresources, comprising means for globally synchronizing a plurality oftasks across a plurality of computational resources, means for computingan amount of work to complete at least one task of the plurality oftasks, means for processing the plurality of tasks in parallel toaccomplish work corresponding to each task of the plurality of tasks,means for repeatedly computing a work fraction that corresponds to oneor more of a fraction of work completed or work remaining to becompleted with respect to the amount of work to complete the at leastone task of the plurality of tasks, and means for modifying acharacteristic of at least one computational resource of the pluralityof computational resources based on the work fraction.

Example 35 may include the apparatus of Example 34, wherein theplurality of computational resources includes a plurality of cores, andwherein a frequency of at least one core of the plurality of cores isvaried based on the work fraction.

Example 36 may include the apparatus of any one of Examples 34 to 35,wherein the plurality of computational resources includes a plurality ofprocessors, and wherein a frequency of at least one core of theplurality of processors is varied based on the work fraction.

Example 37 may include the apparatus of any one of Examples 34 to 36,wherein the plurality of computational resources includes a plurality ofnodes, and wherein at least two nodes of the plurality nodes processparallel code.

Example 38 may include the apparatus of any one of Examples 34 to 37,wherein the plurality of tasks includes a plurality of threads, andwherein the plurality of computational resources includes a plurality ofcores.

Example 39 may include the apparatus of any one of Examples 34 to 38,further including means for receiving an indication of the work fractionat a runtime monitor.

Example 40 may include the apparatus of any one of Examples 34 to 39,further including means for varying one or more of a number, adistribution, a speed, or a frequency of at least one of the pluralityof computational resources.

Example 41 may include the apparatus of any one of Examples 34 to 40,wherein the characteristic includes a speed, and wherein the speed of atleast one computational resource of the plurality of computationalresources is varied by changing an amount of electrical power providedto the at least one computational resource.

Example 42 may include the apparatus of any one of Examples 34 to 41,wherein the plurality of computational resources include one or more ofa core, a processor, a multi-core processor, a node, a cabinet, acluster, a row, or a grid.

Example 43 may include the apparatus of any one of Examples 34 to 42,wherein the plurality of computational resources are in communicationwith one another.

Example 44 may include the apparatus of any one of Examples 34 to 43,wherein the plurality of computational resources includes groups ofcores, and wherein the apparatus further includes means for determininga measurement of an operating characteristic of at least one group ofthe groups of cores, and means for modifying a speed of at least onegroup of the groups of cores based on the measurement.

Example 45 may include the apparatus of any one of Examples 34 to 44,wherein the groups of cores are nodes, and wherein the apparatus furtherincludes means for calculating a skew of a plurality of measurements ofan operating characteristic for a plurality of nodes, and means formodifying a speed of at least one node based on the skew.

Example 46 may include an apparatus for balancing a plurality ofcomputational resources, comprising a plurality of nodes, each nodehaving a progress meter capable of determining progress informationincluding a total amount of work to be done to complete a task and anamount of work that has been done to complete the task, and aperformance balancer that uses the progress information to control thebehavior of the plurality of nodes.

Example 47 may include the apparatus Example 46, further including arun-time monitor to obtain the progress information and forward theprogress information to the performance balancer.

Example 48 may include the apparatus of any one of Examples 46 to 47,wherein the run-time monitor obtains the progress information via one ormore of an explicit function call or a query by the run-time monitor.

Example 49 may include the apparatus of any one of Examples 46 to 48,wherein the run-time monitor includes an application programminginterface (API).

Example 50 may include the apparatus of any one of Examples 46 to 49,wherein the performance balancer is to balance the plurality of nodes byspeeding up a first portion of the plurality of nodes and by slowingdown a second portion of the plurality of nodes.

Example 51 may include the apparatus of any one of Examples 46 to 50,wherein the performance balancer is to increase an amount of electricalpower supplied to a portion of the plurality of nodes to speed up theportion of the plurality of nodes.

Example 52 may include the apparatus of any one of Examples 46 to 51,wherein the performance balancer is to reduce an amount of electricalpower supplied to a portion of the plurality of nodes to slow down theportion of the plurality of nodes.

Example 53 may include a method of controlling computational resources,comprising globally synchronizing a plurality of threads across aplurality of computational resources, making one or more determinationsof an extent to which a thread has been processed, and computing amountsof work to complete each thread of the plurality of threads, wherein theone or more determinations are used to control at least onecomputational resource of the plurality of computational resources.

Example 54 may include the method of Example 53, wherein thecomputational resources include cores.

Example 55 may include the method of any one of Examples 53 to 54,wherein the computational resources include nodes.

Example 56 may include the method of any one of Examples 53 to 55,wherein the computational resources include cabinets.

Example 57 may include the method of any one of Examples 53 to 56,wherein the computational resources include clusters.

Example 58 may include the method of any one of Examples 53 to 57,wherein the computational resources include grids.

Example 59 may include a method of enhancing operating efficiency of aplurality of computational resources, comprising globally synchronizinga plurality of threads across a plurality of cores, computing an amountof work to complete each thread of the plurality of threads, processingthe plurality of threads in parallel to accomplish work corresponding toeach thread of the plurality of threads, repeatedly computing a workfraction that corresponds to a fraction of work completed or remainingto be completed with respect to the amount of work to complete eachthread of the plurality of threads, and modifying a core frequency of atleast one core of the plurality of cores based on the work fraction.

Example 60 may include the method of Example 59, wherein the cores aregrouped into nodes.

Example 61 may include the method of any one of Examples 59 to 60,wherein the nodes are grouped into cabinets.

Thus, techniques and structures described herein may reduce powerconsumption in a graphics processor, and are applicable to other typesof processors as well. As a result, a graphics processor and/or othertypes of processors in which these techniques and structures are usedmay provide relatively higher energy efficiency.

Various embodiments and various modules may be implemented usinghardware elements, software elements, or a combination of both. Examplesof hardware elements may include processors, microprocessors, circuits,circuit elements (e.g., transistors, resistors, capacitors, inductors,and so forth), integrated circuits, application specific integratedcircuits (ASIC), programmable logic devices (PLD), digital signalprocessors (DSP), field programmable gate array (FPGA), logic gates,registers, semiconductor device, chips, microchips, chipsets, and soforth. Examples of software may include software components, programs,applications, computer programs, application programs, system programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof.Determining whether an embodiment may be implemented using hardwareelements and/or software elements may vary in accordance with any numberof factors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints.

Example sizes/models/values/ranges may have been given, althoughembodiments are not limited to the same. As manufacturing techniquesmature over time, it may be expected that devices of smaller size andsmaller tactile element size could be manufactured. In addition, wellknown electrical or fluidic components may or may not be shown withinthe figures, for simplicity of illustration and discussion, and so asnot to obscure certain aspects of the embodiments. Further, arrangementsmay be shown in block diagram form in order to avoid obscuringembodiments, and also in view of the fact that specifics with respect toimplementation of such block diagram arrangements are highly dependentupon the platform within which the embodiment may be to be implemented,i.e., such specifics should be well within purview of one skilled in theart. Where specific details (e.g., circuits) are set forth in order todescribe example embodiments, it should be apparent to one skilled inthe art that embodiments may be practiced without, or with variation of,these specific details. The description may be thus to be regarded asillustrative instead of limiting.

The term “coupled” may be used herein to refer to any type ofrelationship, direct or indirect, between the components in question,and may apply to electrical, mechanical, fluid, optical,electromagnetic, electromechanical or other connections. In addition,the terms “first”, “second”, etc. may be used herein only to facilitatediscussion, and carry no particular temporal or chronologicalsignificance unless otherwise indicated. Additionally, it may beunderstood that the indefinite articles “a” or “an” carries the meaningof “one or more” or “at least one”. As used in this application and inthe claims, a list of items joined by the term “one or more of” may meanany combination of the listed terms. For example, the phrases “one ormore of A, B or C” may mean A; B; C; A and B; A and C; B and C; or A, Band C.

Those skilled in the art will appreciate from the foregoing descriptionthat the broad techniques of the embodiments can be implemented in avariety of forms. Therefore, while the embodiments have been describedin connection with particular examples thereof, the true scope of theembodiments should not be so limited since other modifications willbecome apparent to the skilled practitioner upon a study of thedrawings, specification, and following claims.

1. A method of controlling a computational resource, comprising:globally synchronizing a plurality of tasks across a plurality ofcomputational resources; computing an amount of work to complete atleast one task of the plurality of tasks; processing the plurality oftasks in parallel to accomplish work corresponding to each task of theplurality of tasks; repeatedly computing a work fraction thatcorresponds to one or more of a fraction of work completed or workremaining to be completed with respect to the amount of work to completethe at least one task of the plurality of tasks; and calculating a skewof a plurality of measurements taken from the plurality of computationalresources; and modifying a characteristic of at least one computationalresource of the plurality of computational resources based on the workfraction and the skew.
 2. The method of claim 1, wherein the pluralityof computational resources includes a plurality of cores, and wherein afrequency of at least one core of the plurality of cores is varied basedon the work fraction.
 3. The method of claim 1, wherein the plurality ofcomputational resources includes one or more of a core, a processor, amulti-core processor, a node, a cabinet, a cluster, a row, or a grid,and wherein at least a portion of the plurality of computationalresources are in communication with one another.
 4. The method of claim1, wherein the plurality of tasks includes a plurality of threads, andwherein the plurality of computational resources includes a plurality ofcores.
 5. The method of claim 1, further including: reporting the workfraction by one or more of an application or an Application ProgrammingInterface (API); and receiving an indication of the work fraction at aruntime monitor.
 6. The method of claim 1, further including modifyingone or more of a number, a distribution, a speed, or a frequency of atleast one of the plurality of computational resources.
 7. The method ofclaim 1, wherein the characteristic includes a speed, and wherein thespeed of at least one computational resource of the plurality ofcomputational resources is modified by changing an amount of electricalpower provided to the at least one computation resource.
 8. The methodof claim 1, wherein the plurality of computational resources includes aplurality of nodes, and wherein the method further includes: calculatinga skew of a plurality of measurements taken from the plurality of nodes;and modifying a speed of at least one node of the plurality of nodesbased a comparison of a characteristic of the at least one node to theskew.
 9. The method of claim 1, further including synchronizing theplurality of tasks at a barrier, wherein each task of the plurality oftasks includes a waiting time at the barrier, and wherein the methodfurther includes repeatedly modifying the characteristic to reduce thewaiting time for the at least one task.
 10. An apparatus to processtasks, comprising: a plurality of computational resources to process aplurality of tasks in parallel, wherein the plurality of tasks are to beglobally synchronized across the plurality of computational resources;progress meter logic, implemented at least partly in fixed functionalityhardware, to: compute an amount of work to complete at least one task ofthe plurality of tasks; and repeatedly compute a work fraction that isto correspond to one or more of a fraction of work completed or workremaining to be completed with respect to the amount of work to completethe at least one task; skew calculator logic to compute a skew of aplurality of measurements taken from the plurality of computationalresources; and performance balancer logic, implemented at least partlyin fixed functionality hardware, to modify a characteristic of at leastone computational resource of the plurality of computational resourcesbased on the work fraction and the skew.
 11. The apparatus of claim 10,wherein the plurality of computational resources is to include aplurality of cores, and wherein the performance balancer logic is tovary a frequency of at least one core of the plurality of cores based onthe work function.
 12. The apparatus of claim 10, wherein theperformance balancer logic is to vary a speed of at least one of theplurality of computational resources by varying an amount of powersupplied to the at least one of the plurality of computationalresources.
 13. The apparatus of claim 10, wherein the performancebalancer logic is to vary a speed of at least two of the plurality ofcomputational resources by steering power from a relatively faster oneof the plurality of computational resources toward a relatively slowerone of the plurality of computational resources.
 14. The apparatus ofclaim 10, wherein the computational resources are to include a pluralityof cores, and wherein the performance balancer logic is to vary a speedof at least one of the plurality of cores by varying an amount of powerprovided to the at least one of the plurality of cores.
 15. Theapparatus of claim 10, further including runtime monitor logic,implemented at least partly in fixed functionality hardware, to receiveinformation from the progress meter logic that is to be indicative ofthe work fraction.
 16. The apparatus of claim 10, wherein the pluralityof computational resources are to include one or more of a core, aprocessor, a multi-core processor, a node, a cabinet, a cluster, a row,or a grid, and wherein at least a portion of the plurality ofcomputational resources are to have a communications channeltherebetween.
 17. The apparatus of claim 10, further including: aplurality of nodes; and skew calculator logic to compute a skew of aplurality of measurements taken from the plurality of nodes, wherein theperformance balancer logic is to vary a speed of at least one of thenodes based on the skew.
 18. The apparatus of claim 10, wherein theperformance balancer logic is to modify one or more of a number, adistribution, a speed, or a frequency of at least one of the pluralityof computational resources.
 19. At least one non-transitory computerreadable storage medium comprising one or more instructions that whenexecuted on a computing device cause the computing device to: globallysynchronize a plurality of tasks across a plurality of computationalresources; compute an amount of work to complete at least one task ofthe plurality of tasks; repeatedly compute a work fraction thatcorresponds to one or more of a fraction of work completed or workremaining to be completed with respect to the amount of work to completethe at least one task of the plurality of tasks; compute a skew of aplurality of measurements taken from the plurality of computationalresources; and modify a characteristic of at least one computationalresource of the plurality of computational resources based on the workfraction and the skew.
 20. The at least one non-transitory computerreadable storage medium of claim 19, wherein the plurality ofcomputational resources is to include a plurality of cores, and whereinthe instructions, when executed on a computing device, cause thecomputing device to modify a frequency of at least one of the pluralityof cores.
 21. The at least one non-transitory computer readable storagemedium of claim 19, wherein the instructions, when executed, cause thecomputing device to: compute the work fraction; and receive informationfrom the progress meter indicative of the work fraction.
 22. The atleast one non-transitory computer readable storage medium of claim 19,wherein the instructions, when executed, cause the computing device tovary a characteristic of operation of at least one computationalresource of the plurality of computational resources.
 23. The at leastone non-transitory computer readable storage medium of claim 19, whereinthe instructions, when executed, cause the computing device to vary anamount of power provided to at least one core of the plurality of cores.24. The at least one non-transitory computer readable storage medium ofclaim 19, wherein the instructions, when executed, cause the computingdevice to allow the plurality of tasks to synchronize at a barrier. 25.The at least one non-transitory computer readable storage medium ofclaim 19, wherein each task of the plurality of tasks includes a waitingtime at the barrier, and wherein the instructions, when executed, causethe computing device to repeatedly modify the characteristic to reduce awaiting time for at least one task.